Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Renovate #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 6, 2023

Mend Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • Dockerfile (dockerfile)
  • .github/workflows/docker-publish.yml (github-actions)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Automerge patch and minor upgrades if they pass tests.
  • If automerging, push the new commit directly to the base branch (no PR).
  • Rebase existing PRs any time the base branch has been updated.
  • Disable semantic prefixes for commit messages and PR titles.
  • Separate major versions of dependencies into individual branches/PRs.
  • Do not separate patch and minor upgrades into separate PRs for the same dependency.
  • Raise PR when vulnerability alerts are detected.
  • Evaluate schedules according to timezone UTC.
  • Apply label renovate to PRs.
  • Group all minor and patch updates together.
  • Default configuration for repositories under ocramius/. Taken from https://github.com/laminas/.github/blob/cbcde244afaa457a5a8fae957581ed9abf2a50da/renovate-config.json
  • If automerging, push the new commit directly to the base branch (no PR).
  • Raise a PR first before any automerging.
  • Require all status checks to pass before any automerging.
  • Apply label dependencies to PRs.
  • Append Signed-off-by: to signoff Git commits.
  • WebProject.xyz organisation renovate config

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

With your current configuration, Renovate will create 4 Pull Requests:

Update docker/build-push-action digest to f8bc7f4
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-digest
  • Merge into: master
  • Upgrade docker/build-push-action to f8bc7f46003ef0cf98b715743d86c2f1ccd01436
Update docker/login-action digest to 5f4866a
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-digest
  • Merge into: master
  • Upgrade docker/login-action to 5f4866a30a54f16a52d2ecb4a3898e9e424939cf
Update docker/metadata-action digest to 1294d94
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-metadata-action-digest
  • Merge into: master
  • Upgrade docker/metadata-action to 1294d94f8ee362ab42b6da04c35f4cd03a0e6af7
Update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: master
  • Upgrade actions/checkout to v4

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


Read more information about the use of Renovate Bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants